Transformable near field communication tag

ABSTRACT

A system is disclosed comprising a near field communication tag that is transformable from a first state to a second state. The system also comprises a server program stored on a non-transitory storage medium that, when executed by a server apparatus, receives a first tag report from a user device in response to the tag being tapped while being in the first state, sends a first response to the user device or to another user device in response to the first tag report being received, receives a second tag report from the user device in response to the tag being tapped while being in the second state, and sends a second response to the user device or to another user device in response to the second tag report being received.

CROSS-REFERENCE TO RELATED APPLICATIONS

None.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

REFERENCE TO A MICROFICHE APPENDIX

Not applicable.

BACKGROUND

Technological advances over the last decades have significantlyincreased the convenience to customers when purchasing groceries andother goods. For example, customers now have the possibility, in a largenumber or even in the majority of cases, of accessing websites hosted bysuppliers of goods and services and of studying offers and productinformation online. Further, customers can, in some cases, even orderfood and beverages on the website of a supermarket and request a homedelivery on a particular day.

More generally, the ordering and home delivery has the advantage ofsimplifying the supply of products to households, because a singlevehicle of a delivery company may deliver large quantities of productsand access a large number of households. This avoids having a largenumber of households participating in traffic as individuals, as manycustomers would otherwise drive back and forth between various stores(such as supermarkets) and shop individually. To summarize, one mayconclude that this de-individualizing of the consumer traffic associatedwith transportation of consumer goods may be a way to promoteenvironmental-friendliness of our societies.

For some customer groups (for example, for the elderly), having to findthe right website to order or re-order desired products and of findingthe right menus for doing so on a website, etc., may be a cumbersometask. In addition, repeatedly performing such tasks may annoy customers,and some customers thus tend to fall back into a routine of drivingaround and exploring stores instead of engaging in more progressiveforms of purchasing behavior involving the use of more recenttechnology. There are thus concerns remaining with respect toenvironment-friendliness of a customer's good purchasing habits and alsowith respect to convenience for the customers.

With the aforementioned advantages, come also particular types ofconcerns such as security issues. When customers shop via the internetand enter credit card information, the possibility exists that sensitivedata is stolen and potentially abused. This means that data security isan increasingly important aspect to always be taken into account in thiscontext as well. As an illustrative example, reference is made toso-called dash devices, which are used to conveniently order (orreorder) products in a particularly easy way. A dash device is a WiFicompatible device that is typically equipped with just a single buttonthat allows directly ordering products via the internet by pressing thebutton. While such a dash device may improve convenience, in particular,for some customer groups, it also raises security concerns.

There is, hence, a need for technological advances suited to address oneor more of the above-mentioned shortcomings.

SUMMARY

In an embodiment, a system is disclosed. The system comprises a nearfield communication tag coupled to a consumer product. The near fieldcommunication tag is transformable from a first state to a second statebased on a state of the consumer product being transitioned from a firststate to a second state. The system also comprises a server programstored on a non-transitory storage medium that, when executed by aserver apparatus, receives a first tag report from a user device inresponse to the NFC tag being tapped while being in the first state andsends a first response from the server apparatus to the user device oranother user device, or prompts another server apparatus to send thefirst response to the user device or another user device, in response tothe first tag report being received. The server program, when executedby the server apparatus also receives a second tag report from the userdevice or another user device in response to the NFC tag being tappedwhile being in the second state and sends a second response from theserver apparatus to the user device or another user device, or promptsanother server apparatus to send the second response to the user deviceor another user device, in response to the second tag report beingreceived. The first tag report is different from the second tag reportand the second response is different from the first response.

In another embodiment, a method is disclosed. The method comprisestapping a near field communication (NFC) tag coupled to a consumerproduct with a user device. The NFC tag is transformable from a firststate to a second state without updating or writing to the NFC tag. Themethod also comprises receiving, by a server program stored on anon-transitory storage medium and executed by a server apparatus, a tagreport comprising registration information from the user device inresponse to the NFC tag being tapped by the user device while in thefirst state and sending, by the server program, a first response fromthe server apparatus to the user device or another user device, orprompting another server apparatus to send the first response to theuser device or another user device, in response to the tag reportcomprising the registration information being received. The methodadditionally comprises receiving, by the server program, an indicationfrom the user device or another user device that the NFC tag is to betransformed to a dash cap in response to sending the first response. TheNFC tag is transformed from the first state to the second state based onreceipt of the indication. The method further comprises sending, by theserver program, a second response from the server apparatus to the userdevice or another user device, or prompting another server to send thesecond response to the user device or another user device in response toreceiving the indication, the second response differing from the firstresponse.

In yet another embodiment, a system is disclosed. The system comprises anear field communication (NFC) tag coupled to a consumer product. TheNFC tag is transformable from a first state to a second state withoutupdating or writing to the NFC tag. The system also comprises a serverprogram stored on a non-transitory storage medium that, when executed bya server apparatus, receives a first tag report from a user device inresponse to the NFC tag being tapped and sends a first response from theserver apparatus to the user device or another user device, or promptsanother server apparatus to send the first response to the user deviceor another user device, in response to the first tag report beingreceived. The server program, when executed by the server apparatus,also receives a second tag report from the user device or another userdevice in response to the NFC tag being tapped after the NFC tag istransformed from the first state to the second state. The first tagreport is different from the second tag report. The server program, whenexecuted by the server apparatus, further sends a second response fromthe server apparatus to the user device or another user device, orprompts another server apparatus to send the second response to the userdevice or the another user device, in response to the second tag reportbeing received. The second response is different from the firstresponse.

These and other features will be more clearly understood from thefollowing detailed description taken in conjunction with theaccompanying drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure, referenceis now made to the following brief description, taken in connection withthe accompanying drawings and detailed description, wherein likereference numerals represent like parts.

FIG. 1 is a schematic representation of steps carried out when using asystem in accordance with the present disclosure.

FIG. 2 is a block diagram of a system according to an embodiment of thedisclosure.

FIG. 3 is a flow chart of a method according to an embodiment of thedisclosure.

FIG. 4 is an illustration of a mobile communication device according toan embodiment of the disclosure.

FIG. 5 is a block diagram of a hardware architecture of a mobilecommunication device according to an embodiment of the disclosure.

FIG. 6A is a block diagram of a software architecture of a mobilecommunication device according to an embodiment of the disclosure.

FIG. 6B is a block diagram of another software architecture of a mobilecommunication device according to an embodiment of the disclosure.

FIG. 7 is a block diagram of a computer system according to anembodiment of the disclosure.

DETAILED DESCRIPTION

It should be understood at the outset that although illustrativeimplementations of one or more embodiments are illustrated below, thedisclosed systems and methods may be implemented using any number oftechniques, whether currently known or not yet in existence. Thedisclosure should in no way be limited to the illustrativeimplementations, drawings, and techniques illustrated below, but may bemodified within the scope of the appended claims along with their fullscope of equivalents.

Aspects of the above-mentioned object are achieved by a systemcomprising a near field communication (NFC) tag coupled to a consumerproduct. This NFC tag overcomes technical problems associated withtraditional NFC tags that may change based on updating/writing to theNFC tag, which requires additional processing. In particular, the NFCtag discussed herein may transition to different states withoutupdating/writing to the NFC tag. The NFC tag may transition to three ormore states without updating/writing to the NFC tag. For example, atransition of the NFC from a first state to a second state may beeffected by a user registering and a transition of the NFC tag from thesecond state to a third state may be the transformation of the NFC tagto a dash cap. The NFC tag may be updated or written to for otherreasons during the life of the NFC tag and/or the life of the consumerproduct, but for the purposes of this application and achieving thestate transitions of the NFC tag to enable particular, differentiatedresponses to one or more user devices, writing to or updating of the NFCtag is not needed.

In one example of the NFC being transitioned to different states withoutupdating/writing to the NFC tag, the NFC tag discussed herein maytransition to different states based on a state of the consumer productbeing transitioned from a first state to a second state such as by useraction (e.g., twisting a cap, which interrupts a formerly closed loop)without requiring processing (e.g., such as by an independent NFCwriter) for a state change, thereby resulting in a simpler, moreefficient, more maintainable, and cost conscious IT solution. Differentinformation may be provided to the user device depending on the state ofthe NFC tag.

In another example of the NFC tag being transitioned to different stateswithout updating/writing to the NFC tag, the NFC tag discussed hereinmay transition to different states based on input to a user device.Registration information may be inputted into the user device andtransmitted to a server. Based on receipt of the registrationinformation, the server may determine that the NFC tag is in a firststate and may send a particular response signal (e.g., that redirectsthe browser to a particular webpage) to the user device based on thatdetermination. Through display of the particular webpage, the user mayobtain product information and may also be able to select an option toturn the NFC tag into a dash cap. A dash cap as used herein may serve asa dash device when used together with the user device to enable directordering of products via the internet. Based on receipt of user inputindicating that the user wants to turn the NFC tag into a dash cap, theNFC tag may be transitioned to a second state without a change to theprogramming of the NFC tag, and a server may send a particular responsesignal (e.g., that redirects the browser to an ecommerce system webpage)to the user device or another user device based on the transition to thesecond state. In an embodiment, the change in the NFC tag from the firststate to the second state is performed by a platform such that when auser subsequently reads or taps the NFC tag with the user device oranother user device, the browser of the user device or another userdevice is directed directly to an ecommerce product specific page toorder the consumer product that the NFC tag is/was coupled to.

In some embodiments, the system presented herein may comprise theconsumer product and a non-transitory storage medium. The consumerproduct and the storage medium may be physically separate and may beused in completely different locations.

The consumer product may, for example, be a container closure (forexample, a bottle lid or cap or a jar lid or cap, etc.). The consumerproduct is provided with a near field communication tag and istransformable from a first state to a second state. A near fieldcommunication tag generally comprises a chip or processor and anantenna. To provide an example, such tag may, for example, be providedon the inside of a bottle lid. The transformability from the first stateto the second state may, for example, be effectable by reversible orirreversible mechanical (or some other form of) action (for example,when a consumer opens a container closure and/or when the consumerseparates the closure from the container, for example, by taking a lidoff a bottle). The transformability may be one-way, i.e., only from thefirst to the second state. For other embodiments, it may be two-way,i.e., also from the second state to the first state. For example, thetag may comprise a loop connected to the chip that can be interrupted tothus change the state of the chip.

The storage medium may be provided with a server program stored thereon.The term “server program” is in this context in this application used torefer to a computer program that provides functionality for otherprograms or devices, sometimes referred to as clients (client-servermodel). In contrast, the term “server apparatus” is in this applicationused to denote a device in the sense of hardware that providesfunctionality for other programs or devices. Servers (as a generic termcovering server apparatuses and server programs) may provide variousfunctionalities such as sharing data or resources amongst severalclients and/or performing computations for a client. A single server mayserve multiple clients, and a single client may use multiple servers. Aclient process may run on the same device or may connect over a networkto a server on a different device.

The near field communication tag and the server program, when run on aserver apparatus, are configured to interact with a user device and,optionally, another user device, so that the server apparatus/program,and the tag are configured to perform the following method steps:

-   -   tapping the near field Communication tag with the user device;    -   sending a first tag report signal from the user device to the        server apparatus if the consumer product was tapped while being        in the first state, and sending a second tag report signal from        the user device to the server apparatus if the consumer product        was tapped while being in the second state, the first tag report        signal differing from the second tag report signal;    -   receiving the first tag report signal and/or the second tag        report signal by the server apparatus;    -   sending a first response signal from the server apparatus to the        user device or to another user device, or prompting another        server apparatus to send a first response signal to the user        device or the another user device, when the first tag report        signal is received; and    -   sending a second response signal from the server apparatus to        the user device or to another user device, or prompting another        server apparatus to send a second response signal to the user        device or the another user device when the second tag report        signal is received, the second response signal differing from        the first response signal.

A first or second tag report signal and a first or second responsesignal may be referred to a first or second report and a first or secondresponse, respectively. Also, a signal may be referred to as a message.The labels “first” and “second” for the tag report signals and for theresponse signals, respectively, are merely labels for distinguishingbetween the respective signals but do not indicate an order or attributeany other feature(s) to the respective signals. Moreover, only thesending steps associated with the first signals or the sending stepsassociated with the second signals may be carried out (the expression“and” does not mean that both is required to be carried outsequentially, but only that the suitability to perform either of thesteps is provided). Moreover, the sending of signals by the serverapparatus “or” the prompting another server apparatus to send thesignals may be considered alternatives, or both may be possiblesimultaneously.

The “tapping” of the tag may, for example, alternatively, be referred toas a “scanning” or “reading” the tag. The user device may be an NFCreader or writer, optionally it may be a mobile device (e.g., asmartphone or a tablet), or another handheld device configured to tapthe tag.

Because different tag report signals are sent from the user device tothe server apparatus, it is possible for the server apparatus to knowwhether the consumer product (e.g., the container closure/cap/lid) is inthe first state or the second state. The consumer product may also beconfigured to be in more than two (for example, in three or more)states, and the discussed steps may be generalized to the case of threeor more states. Depending on the state of the consumer product,different response signals may thus be sent back from the serverapparatus or another server apparatus to the user device or another userdevice.

To provide examples, the server apparatus (for example, hosted by afirst provider, for example, the producer of the consumer product) mayredirect to another server (e.g., hosted by another provider, forexample, the manufacturer of the container or the content thereof).Either of these may send back a response signal, selectively dependingon the state of the tag, to the user device (e.g., the smartphone) or toanother user device (e.g., a consumer's laptop or tablet that may beassociated with the smartphone through some user ID connection etc.).

To provide a concrete example illustrating the more generally describedaspects, the tag inside of a cap of a closed bottle may be tapped by asmartphone. The smartphone may then send a first tag report signal to afirst server (a server that may, for example, be hosted by themanufacturer of the cap). The first server may then redirect to a secondserver (e.g., hosted by the manufacturer of bottle or content thereofsuch as liquor). The second server may then send a response signal tothe smartphone, for example, a signal including an URL associated withthe website belonging to the company hosting the second server. Thewebsite may then be displayed on the consumer's smartphone and offer,for example, product information.

When the consumer opens the bottle (e.g. after purchasing it), amechanical action takes place. This action may break a part of the tag(for example, a formerly closed loop may be interrupted, as mentionedabove), but this does not render the tag non-functional (as it, forexample, still comprises a working chip or processor and antenna). Theconsumer may then again tap the tag (now residing in a second state).This may be considered also a form of tamper evidence mechanism, as thesecond tag report signal now contains (be it implicitly) the informationthat the bottle has been opened, whereas before opening the first tagreport signal did not contain this information.

Now, a chain of communication depending from the second tag reportsignal may involve the second server sending a response signal to thesmartphone (or a tablet, etc.) with an URL guiding directly to an orderform for re-ordering bottles, or to a login form so that a user canlogin and then select to transform the tag into a device that may serveas a dash device when used together with the smartphone.

The possibility of this exemplified consumer product state-dependentcommunication between tag, user device, and server may increase consumerconvenience. This way, it may also contribute toenvironment-friendliness because the consumer product's lifecycle may beextended. For example, non-discarding the consumer product after usingit in the context of its first functionality (i.e., being a containerclosure) may be made more attractive to consumers. The consumer productmay also enter a second stadium of its lifecycle by taking on a secondfunctionality by serving to order products together with a smartphone.In addition thereto or alternatively thereto, the consumer product mayalso be provided with additional features, for example, a voucher code,etc. All of these aspects may increase the product status in the eyes ofconsumers thereby promoting a more environment-friendly handling ofconsumer products such as container closures, for example, bottle caps,lids, screw tops, etc.

Additionally, the tag of the consumer product is itself a passive devicein the sense that it is not linked to a WiFi network. Thus, the securityfor consumers is also improved in case the tag is provided with afunctionality associated with sensitive actions such as purchasingproducts (for example, involving the use of credit card or othersensitive data, etc.).

The tapping may involve sending an initiation signal from the userdevice to the tag and the sending of a reaction signal from the tag tothe user device. Thus, it is not a requirement for the tag to have itsown energy source (such as a battery).

As mentioned, the tag may comprise at least one loop, and the tag may beconfigured to send a first reaction signal to the user device when theat least one loop is intact. The loop is breakable by a consumermanipulating the consumer product. The breaking may be effectedmechanically. For example, the at least one loop may be broken when aconsumer removes the consumer product in the form of a container closurefrom the container (e.g., unscrewing a cap from a bottle). Saidmanipulation may take place within the consumer product itself or it maytake place between the consumer product and an external object (like inthe case of a bottle lid being removed/screwed/drawn off a bottle). Thetag may be configured to send a second reaction signal to the userdevice when the loop is broken. The user device may be configured tosend out the first tag report signal if it receives the first reactionsignal and to send out the second tag report signal if it receives thesecond reaction signal.

According to some embodiments, the tag comprises at least one loop, andthe user device is configured to send the first tag report signal to theserver apparatus when the at least one loop is intact, wherein the loopis breakable by a consumer manipulating the consumer product, thebreaking optionally to be effected mechanically, wherein the user deviceis configured to send the second tag report signal to the serverapparatus when the loop is broken.

The consumer product may be a container closure for closing a container,and the tag may be configured such that the one loop is broken when aconsumer removes the closure from the container.

The tag may be provided on the inside of the container closure. Forexample, the inside of the closure may further be provided withinformation such as a voucher code or a (tag) ID number or some othercode which a user can enter to register on a website hosted by theserver apparatus or another server apparatus, or to turn the tag into adash device component (changing state).

The consumer product may be a closure of a container such as a bottle orjar. This may be particularly advantageous when combined with theordering scheme using the dash-transformed tag, as consumers may beespecially prone to drive around individually to pick up largerquantities of beverages due to heavy weight of a large number ofbottles, etc. Another option is that the tag is used to activate apickup service for empty bottles (for example, empty beer bottles are tobe picked up, etc.). This may further promoteenvironmental-friendliness.

The system may comprise the server apparatus including thenon-transitory storage medium. Alternatively, the system may include theserver apparatus with a different internal or externalized storagemedium onto which the server program on the non-transitory storagemedium of the system can be copied.

According to some embodiments, the server apparatus, when running theserver program thereon, is configured to send a prompting signal to theanother server apparatus in order to prompt the sending of the first orsecond or third, etc., response signal.

The first response signal may include a uniform resource locator and/orthe second response signal may include a uniform resource locator. Thisway, the user device (or another user device) may be provided withselective URL information and, for example, a browser installed on theuser device can be fed with the selective URL to display selectivewebsite content.

According to some embodiments, the consumer product may in the firststate be configured to be used as a container closure for closing acontainer, and the consumer product may in the second state beconfigured to be attached to a surface of an external object.

The consumer product may be configured to be transitioned from the firstto the second state by an input in the user device or another userdevice (e.g., by registering and/or logging in and/or using a tag ID orsome other code that may be provided with or on the consumer product).For example, the tag may be turned from consumer product (e.g., bottlelid) into a form of dash device configured to interact with asmartphone, etc.

The user device may be a smartphone or another type of NFC reader or NFCwriter, a tablet, a computer, a laptop, and/or the another user devicemay be a smartphone or another type of NFC reader or NFC writer, atablet, a computer, a laptop, etc.

The second tag report signal may include order information for orderingor re-ordering a product, for example, it may be information fordirectly ordering one or products such as jars or bottles with a productprovided therein (e.g., wine, beer, soft drinks, cocktails, liquor,etc.).

The system may be further configured to interact so as to perform thesteps of: displaying a first website content on the user device or theanother user device upon receiving the first response signal anddisplaying a second website content, differing from the first websitecontent, on the user device or the another user device upon receivingthe second response signal.

The server apparatus is according to some embodiments, when running theserver program, configured to interact with the user device or theanother user device so as to perform the following method steps:entering registration information, optionally an identification numberof the tag, on the user device; sending the registration information tothe server; and wherein the server apparatus is configured to send thesecond response signal or prompt another server to send the secondresponse signal after receiving the registration information only; orthe server is configured to send a third response signal or promptanother server to send a third response signal after receiving theregistration information, the third response signal differing from thefirst response signal and from the second response signal. This conceptmay be extended to four or more states and signals, etc.

Another aspect of this disclosure relates to a method of communicatingbetween a user device, a server apparatus with a server program storedthereon, and a consumer product provided with a near field communicationtag, said consumer product being transformable from a first state to asecond state, the method optionally comprising any one or several (anycombination) of the previously described method steps that any of theaspects (or combinations thereof) of the system are configured toexecute (or, more generally, for which the aspects of the system canparticipate in the execution).

Another aspect of this disclosure relates to a non-transitory storagemedium assembly with a first program stored thereon and a second programstored thereon, the assembly comprising at least one non-transitorystorage medium, wherein the first program and the second program may bestored on the same storage medium or on two different storage mediums,the first program being configured to be executed on a user device,optionally a smartphone, the second program being configured to beexecuted on a server apparatus, wherein the first and second programsare configured to cause the user device and the server apparatus tointeract with a consumer product provided with a near fieldcommunication tag, so as to perform the method steps of in accordancewith any one or several (any combination) of any of the previouslydescribed aspects.

Another aspect of this disclosure relates to a system comprising aconsumer product and a non-transitory storage medium assembly, thenon-transitory storage medium assembly being provided with a firstprogram stored thereon and a second program stored thereon, the assemblycomprising at least one non-transitory storage medium, wherein the firstprogram and the second program may be stored on the same storage mediumor on two different storage mediums, the first program being configuredto be executed on a user device, optionally a smartphone, the secondprogram being configured to be executed on a server apparatus, whereinthe first and second programs are configured to cause the user deviceand the server apparatus to interact with a consumer product providedwith a near field communication tag, so as to perform the followingmethod steps: entering information in the user device to transform theuser device from a first state to a second state; tapping the near fieldcommunication tag with the user device; sending a first tag reportsignal from the user device to the server apparatus if the user deviceis in the first state, and sending a second tag report signal from theuser device to the server apparatus if the user device is in the secondstate, the first tag report signal differing from the second tag reportsignal; receiving the first tag report signal and/or the second tagreport signal by the server apparatus; sending a first response signalto the user device or to another user device by the server apparatus, orprompting another server apparatus to send a first response signal tothe user device or the another user device, when the first tag reportsignal is received; and sending a second response signal to the userdevice or to another user device by the server apparatus, or promptinganother server apparatus to send a second response signal to the userdevice or the another user device when the second tag report signal isreceived, the second response signal differing from the first responsesignal.

Additional advantages and features of the present disclosure, that canbe realized on their own or in combination with one or several featuresdiscussed above, insofar as the features do not contradict each other,will become apparent from the following description of particularembodiments.

Now turning to FIG. 1, the system itself (not shown) comprises aconsumer product and a non-transitory storage medium. In this case, theconsumer product is a closure (a bottle cap), and the content of thestorage medium has been copied and stored on machinery (to be describedin the following) that can be used to carry out data communication stepsas follows.

In the case of this embodiment, the bottle lid in question is providedon a liquor bottle. Other embodiments of closures may be provided ondifferent containers (e.g., fluid containers) such other bottles (e.g.,wine or beer bottles) or jars, etc.

The closure is provided with a near filed communication tag on theinside, and it is possible to tap (“scan”/“read”) the tag from theoutside of the bottle, just by holding a suitable user device configuredas a NFC tag reader against the closure. A consumer thus conveniently“taps” the closure (step S1) with the user device. The user device isinternet compatible and, upon receiving the message, the user devicesends a message to an IOT (“Internet of Things”) platform and is thenredirected to a landing webpage (URL) in a browser, for example, thebrowser of a smartphone.

In the case of the embodiment of FIG. 1, the user device is a smartphone. To carry out the tapping of the tag, the user device emits aninitiation signal (providing the energy needed to trigger a responsefrom the NFC tag). In response, the NFC tag on the closure sends a tagreport signal to the smart phone. The tag report signal may be based ona simple NDEF exchange protocol (SNEP) and may contain information suchas a uniform resource locator (URL).

On said smart phone, a web browser is stored, and the tapping of theclosure results in the browser opening a webpage (S2) hosted by a firstserver. The website hosted by the first server is schematicallyrepresented as functional block 100 in FIG. 1. The term “first server100” is, in this context, used to refer to a server program stored on aserver (the latter referring to a “server” in the sense of hardware).

The first server 100 collects user data transferred by the smart phone(step S3) that is (partially or fully) based on the information read outfrom the tag. Then, a check is performed (step S4) whether the specifiedURL is correct (e.g., whether the URL specified by the tag correspondsto the website hosted by the first server 100) and whether a databasecontains a UID (a unique identifier/a unique identification code such asa number) corresponding to the tapped tag.

If the check in step S4 produces a negative result (wrong URL or invalidUID), i.e., “FALSE” in block diagram 100, a “fake closure” is identifiedand the procedure ends. This protects against faking of a product suchas a bottle with a closure and/or a closure and may thus increase safetyfor consumers. If, on the contrary, the check (S4) yields a positiveresult (correct URL and valid UID), a database on the first server 100is updated (for example, a counter may increase a counter number thatcounts how often the tag has been tapped). For example, when a bottle isstanding in a store, the counter number may be increased by one, and thefirst server 100 knows how often the bottle (closure) has been tapped.Alternatively or in addition thereto, other updated to a database can beperformed. For example, the location of the tag may be identified (i.e.,it may be established that it is positioned in a particular store orother location via location information transferred from the userdevice).

If the check (S4) is successful, a response signal is generated (stepS5) by the first server 100. The response signal is a redirection of URLand is sent back to the consumer's smart phone to redirect the browserto another webpage. Which URL the browser is redirected to by theresponse signal may depend on a state of the NFC tag on the bottle. Forexample, the browser may be directed to a “landing page” (step S6)hosted by a second server, schematically represented by block diagram102.

The second server 102 sends a response signal to the smart phone. Moregenerally, the smart phone and the second server 102 communicate toexchange data as will be detailed in the following. For example, in thecase of this embodiment, the smart phone displays a landing page of thewebsite corresponding to the second server 102, and the consumer isoffered the possibility to turn the tapped NFC tag into a dash cap whichcan then be used to directly order further products very conveniently.

The consumer is presented with the option of pressing one or severalbuttons on the website of the second server 102 (step S7). Depending onwhat the consumer selects, the browser redirects to particular webpages(for example, detailed information about the product in the bottle,represented by “Option1” in block diagram 102). The consumer can alsoturn the tag into a dash cap. In this embodiment, the consumer ispresented with a mask for entering registration information (step S8).Such a registration may typically take place when a user has bought thebottle, consumed the content, and now wishes to easily and convenientlyreorder the product. The consumer can take the lid and turn it into adash cap and then keep it in a convenient position, e.g., on the fridgein the kitchen. The closure of the bottle may, to this end, be providedwith a magnet (or some other attachment means) allowing convenientplacement and storing at a chosen location.

To avoid misunderstandings or unwanted transformation of state of theclosure with the tag, this embodiment asks a consumer (with a message onthe screen of the smart phone), whether she or he is sure about turningthe tag into a dash cap (step S9). If the consumer answers “no”, thenthe browser is redirected to the landing page of the second server 102.If the consumer answers affirmatively, however, then the state of thetag is transformed, and it then enters a second phase of its lifecycleas a consumer product. It may then serve as a product and/or brandindividualized dash cap.

Turning back to step S5 of redirection of URL of the first server 100,if the tag has been transformed to a dash cap, the redirection may beeffected to an ecommerce system webpage (hosted by the first server 100in the case of this embodiment). This is represented as step S10 in FIG.1.

On the ecommerce webpage of the first server 100, a consumer ispresented with the option of logging in (by reentering the login dataspecified earlier on in the registration process of step S8).Alternatively, according to some embodiments, a consumer may wish tostay logged in permanently. The step of logging in is represented asstep S11 in FIG. 1.

When logged in, the consumer can conveniently specify (step S12) thenumber of bottles of a specific brand to be ordered on a webpage openedin the smart phone's browser and then click to confirm the order (stepS13) on the browser of the smartphone. The ordered bottles may then,e.g., be delivered to a selected address.

As just described, a consumer may in this way first use the closureincluding the NFC tag as a bottle lid until the bottle has been emptiedor until there is no desire to continue using the closure. The consumermay then decide to use the closure for a different purpose, and in thisway, the closure including the NFC tag may enter a second phase of itslife cycle in which it exerts a functionality that differs from theearlier functionality of serving as a closure for a container. This mayincrease the product status in the eyes of consumers. This in turn maypromote a more environment-friendly handling of container closures suchas bottle caps, lids, screw tops, etc.

The NFC tag does not need to change status and/or programming, so thatthe NFC tag may always remain in the same state during the first partand the second part of its life cycle. A change may, however, beperformed to an IOT platform such that when a user reads (taps) the NFCtag in a bottle lid/cap (or some other container closure) before orafter opening the container, the consumer is then led to differentwebsites. For example, the consumer may tap the bottle lid of a closedbottle in a supermarket and the smartphone may then, for example,automatically open up the brand manufacturer's website (after havingreceived a signal from the server or from another server communicatingwith said server).

A different state may, however, be reached if the user opens thecontainer (for example, the bottle). When the container is opened (forexample, the cap containing the NFC tag is moved to open the bottle), aloop may be broken. If the loop is broken, this information is conveyedto the smartphone (not shown in FIG. 1). The information that the loophas been broken may be used to change the information presented to auser on the smartphone. The consumer may then be presented with adifferent website associated with a different URL.

Another way of ensuring that the container has been opened is that aconfirmation code is provided on the inside of the closure, wherein theconsumer may enter the confirmation code on the website. The consumer isthen redirected to a different part of the website. For example, theclosure with the NFC tag may then acquire a new function of an orderingtool. The consumer can tap it to send a signal with the smartphone to aserver for ordering another container (e.g., another bottle). This way,the function of a dash device can be replaced by the closure and thesmartphone.

In this regard, it is optionally ensured that transforming the containerclosure from a closure to a dash-type of ordering device by mistake isavoided. For example, after having opened a container, the user may, forexample, when tapping the tag, be presented with the option on thewebsite displayed on the tapping device (e.g., the smartphone) of makinga dash cap. From this land page menu, as described above, the consumercan choose the option and be guided into a login or short procedure ofregistration on the ecommerce website. If not already registered, theconsumer will be asked to fill in typical basic information to create anaccount, and will then be allowed repetitive ordering of products(delivery address, billing address, payment method). At the end of sucha successful procedure, the IOT platform will change the re-directingaddress of the NFC, sending the consumer directly to the ecommerceproduct specific page. The consumer may then, for example, be presentedwith the option of simply tapping the cap to order (or re-order)products. Further, a password protection mechanism may be integrated. Insome cases, a specific kind of tag (DNA tag) with a UID number of thetag may also work as a protection against frauds.

The use of a closure with a NFC tag instead of a dash device inaccordance with prior art may offer the advantage of sparing a consumerfrom having to buy a separate device as the consumer can instead justuse the closure together with a NFC reader (for example, a smartphone).The closure with the NFC tag also does not depend on a WiFi connection.It can just be used together with the smartphone, for example, whereverdesired. It also very easy to use the closure provided with the NFC tagin different places. For example, the closure may be provided with someattachment means for attaching the closure to a surface of an externalobject. For example, the closure may be provided with a magnet and maybe attached to a fridge or another piece of kitchen furniture. A closureincluding an NFC tag may be placed in an appropriate location of choice,for example, in the household, or it may be used as a key holder. Asdiscussed, it may be provided with the functionality of contributing tothe process of re-ordering a product in question (for example, thecontainer with which the closure was used and/or other productsmanufactured by the same company).

Another option is that the “opened closure” is used as a purchasingproof and may, for example, be used once (or repeatedly) in the form ofa voucher to get discounts (for example, when re-ordering products).This may be used to provide a further incentive for users to engage inenvironment-friendly and responsible product purchasing behavior.

Now turning to FIG. 2, a system 200 is described. In an embodiment, thesystem comprises a near field communication (NFC) tag 202. In anembodiment, the NFC tag 202 is an NFC tag as discussed above withrespect to FIG. 1. While described as an NFC tag, in some embodiments,the NFC tag 202 may be some other type of radio frequency identificationtag. The NFC tag 202 may be coupled to a consumer product 204. Forexample, the consumer product 204 may be a container and the NFC tag 202may be coupled to a container closure. Coupled as used herein comprisesdirectly or indirectly coupled. In an embodiment, the consumer product204 is a consumer product as discussed above with respect to FIG. 1.

In an embodiment, the system 200 also comprises a user device 206. Theuser device 206 may comprise a mobile device such as a smart phone asdiscussed above with respect to FIG. 1. Mobile devices are discussedfurther hereinafter. The user device 206 may comprise a cellular radiotransceiver (not shown) that may be able to establish a wirelesscommunication link to a cell site 208 which communicatively links theuser device 206 to a network 210. The user device 206 may furthercomprise a WiFi radio transceiver (not shown) that may establish awireless communication link to a WiFi access point (AP) 212 whichcommunicatively links the user device 206 to the network 210. The userdevice 206 may further comprise a processor, a display, and anon-transitory memory. The memory may store one or more applicationssuch as a client program.

The user device 206 may be a mobile phone, a smart phone, a personaldigital assistant (PDA), a media player, a wearable computer, a headsetcomputer, a laptop computer, a notebook computer, or a tablet computer.The cell site 208 may be an enhanced Node B (eNB), a base transceiverstation (BTS), a picocell, or other cellular radio access network (RAN)access point. The cell site 208 may provide a cellular wirelesscommunication link to the user device 206 according to at least one of along-term evolution (LTE), a code division multiple access (CDMA), aglobal system for mobile communications (GSM), or a worldwideinteroperability for microwave access (WiMAX) cellular telecommunicationprotocol. The system 200 may comprise any number of user devices 206,any number of cell sites 208, and any number of WiFi APs 212.

The system 200 may also comprise a server apparatus 214, which may beimplemented as a computer system. Computer systems are described furtherhereinafter. The server apparatus 214 may comprise the server apparatusdiscussed above with respect to FIG. 1. In an embodiment, the serverapparatus 214 may comprise one or more applications such as a serverprogram. In an embodiment, the server program, when executed by theserver apparatus 214, receives a first tag report from the user device206 in response to the NFC tag 202 being tapped and sends a firstresponse from the server apparatus 214 to the user device 206 or anotheruser device, or prompts another server apparatus to send a firstresponse to the user device 206 or another user device, in response tothe first tag report being received. The server program may also receivea second tag report from the user device 206 or another user device inresponse to the NFC tag 202 being tapped after the NFC tag 202 istransformed from a first state to a second state and sends a secondresponse from the server apparatus 214 to the user device 206 or anotheruser device, or prompts another server apparatus to send a secondresponse to the user device 206 or another user device, in response tothe second tag report being received. The first tag report may bedifferent from the second tag report and the second response may bedifferent from the first response.

In an embodiment, the NFC tag 202 may be transformed from the firststate to the second state based on user input to a user device (e.g.,user device 206). In another embodiment, the NFC tag 202 may betransformed from the first state to the second state based on a state ofthe consumer product being transitioned from a first state to a secondstate such as by user action (e.g., twisting a cap, which interrupts aformerly closed loop). In both embodiments, the NFC tag 202 may betransformed from the first state to the second state without writing toor updating the NFC tag 202.

The network 210 comprises one or more private networks, one or morepublic networks, or a combination thereof. The network 210 promotescommunication as desired among the server apparatus 214 and the userdevice 206.

Turning now to FIG. 3, a method 300 is described. At block 302, a userdevice taps a near field communication (NFC) tag coupled to a consumerproduct. The NFC tag is transformable from a first state to a secondstate without updating or writing to the NFC tag. At block 304, a serverprogram stored on a non-transitory storage medium and executed by aserver apparatus receives a tag report comprising registrationinformation from the user device in response to the NFC tag coupledbeing tapped by the user device while in the first state. At block 306,the server program sends a first response from the server apparatus tothe user device or to another user device, or prompts another serverapparatus to send the first response to the user device or another userdevice, in response to the tag report comprising the registrationinformation being received. At block 308, the server program receives anindication from the user device or another user device that the NFC tagis to be transformed to a dash cap in response to sending the firstresponse. The NFC tag is transformed from the first state to the secondstate based on receipt of the indication. At block 310, the serverprogram sends a second response from the server apparatus to the userdevice or to another user device, or prompts another server to send thesecond response to the user device or another user device in response toreceiving the indication. The second response is different from thefirst response.

FIG. 4 depicts the user equipment (UE) 400, which is operable forimplementing aspects of the present disclosure, but the presentdisclosure should not be limited to these implementations. Thoughillustrated as a mobile phone, the UE 400 may take various formsincluding a wireless handset, a pager, a personal digital assistant(PDA), a gaming device, or a media player. The UE 400 includes atouchscreen display 402 having a touch-sensitive surface for input by auser. A small number of application icons 404 are illustrated within thetouch screen display 402. It is understood that in differentembodiments, any number of application icons 404 may be presented in thetouch screen display 402. In some embodiments of the UE 400, a user maybe able to download and install additional applications on the UE 400,and an icon associated with such downloaded and installed applicationsmay be added to the touch screen display 402 or to an alternativescreen. The UE 400 may have other components such as electro-mechanicalswitches, speakers, camera lenses, microphones, input and/or outputconnectors, and other components as are well known in the art. The UE400 may present options for the user to select, controls for the user toactuate, and/or cursors or other indicators for the user to direct. TheUE 400 may further accept data entry from the user, including numbers todial or various parameter values for configuring the operation of thehandset. The UE 400 may further execute one or more software or firmwareapplications in response to user commands. These applications mayconfigure the UE 400 to perform various customized functions in responseto user interaction. Additionally, the UE 400 may be programmed and/orconfigured over-the-air, for example from a wireless base station, awireless access point, or a peer UE 400. The UE 400 may execute a webbrowser application which enables the touch screen display 402 to show aweb page. The web page may be obtained via wireless communications witha base transceiver station, a wireless network access node, a peer UE400 or any other wireless communication network or system.

FIG. 5 shows a block diagram of the UE 400. While a variety of knowncomponents of handsets are depicted, in an embodiment a subset of thelisted components and/or additional components not listed may beincluded in the UE 400. The UE 400 includes a digital signal processor(DSP) 502 and a memory 504. As shown, the UE 400 may further include anantenna and front end unit 506, a radio frequency (RF) transceiver 508,a baseband processing unit 510, a microphone 512, an earpiece speaker514, a headset port 516, an input/output interface 518, a removablememory card 520, a universal serial bus (USB) port 522, an infrared port524, a vibrator 526, one or more electro-mechanical switches 528, atouch screen liquid crystal display (LCD) with a touch screen display530, a touch screen/LCD controller 532, a camera 534, a cameracontroller 536, and a global positioning system (GPS) receiver 538. Inan embodiment, the UE 400 may include another kind of display that doesnot provide a touch sensitive screen. In an embodiment, the UE 400 mayinclude both the touch screen display 530 and additional displaycomponent that does not provide a touch sensitive screen. In anembodiment, the DSP 502 may communicate directly with the memory 504without passing through the input/output interface 518. Additionally, inan embodiment, the UE 400 may comprise other peripheral devices thatprovide other functionality.

The DSP 502 or some other form of controller or central processing unitoperates to control the various components of the UE 400 in accordancewith embedded software or firmware stored in memory 504 or stored inmemory contained within the DSP 502 itself. In addition to the embeddedsoftware or firmware, the DSP 502 may execute other applications storedin the memory 504 or made available via information carrier media suchas portable data storage media like the removable memory card 520 or viawired or wireless network communications. The application software maycomprise a compiled set of machine-readable instructions that configurethe DSP 502 to provide the desired functionality, or the applicationsoftware may be high-level software instructions to be processed by aninterpreter or compiler to indirectly configure the DSP 502.

The DSP 502 may communicate with a wireless network via the analogbaseband processing unit 510. In some embodiments, the communication mayprovide Internet connectivity, enabling a user to gain access to contenton the Internet and to send and receive e-mail or text messages. Theinput/output interface 518 interconnects the DSP 502 and variousmemories and interfaces. The memory 504 and the removable memory card520 may provide software and data to configure the operation of the DSP502. Among the interfaces may be the USB port 522 and the infrared port524. The USB port 522 may enable the UE 400 to function as a peripheraldevice to exchange information with a personal computer or othercomputer system. The infrared port 524 and other optional ports such asa Bluetooth® interface or an IEEE 802.11 compliant wireless interfacemay enable the UE 400 to communicate wirelessly with other nearbyhandsets and/or wireless base stations. In an embodiment, the UE 400 maycomprise a near field communication (NFC) transceiver. The NFCtransceiver may be used to complete payment transactions withpoint-of-sale terminals or other communications exchanges. In anembodiment, the UE 400 may comprise a radio frequency identify (RFID)reader and/or writer device.

The switches 528 may couple to the DSP 502 via the input/outputinterface 518 to provide one mechanism for the user to provide input tothe UE 400. Alternatively, one or more of the switches 528 may becoupled to a motherboard of the UE 400 and/or to components of the UE400 via a different path (e.g., not via the input/output interface 518),for example coupled to a power control circuit (power button) of the UE400. The touch screen display 530 is another input mechanism, whichfurther displays text and/or graphics to the user. The touch screen LCDcontroller 532 couples the DSP 502 to the touch screen display 530. TheGPS receiver 538 is coupled to the DSP 502 to decode global positioningsystem signals, thereby enabling the UE 400 to determine its position.

FIG. 6A illustrates a software environment 602 that may be implementedby the DSP 502. The DSP 502 executes operating system software 604 thatprovides a platform from which the rest of the software operates. Theoperating system software 604 may provide a variety of drivers for thehandset hardware with standardized interfaces that are accessible toapplication software. The operating system software 604 may be coupledto and interact with application management services (AMS) 606 thattransfer control between applications running on the UE 400. Also shownin FIG. 6A are a web browser application 608, a media player application610, and JAVA applets 612. The web browser application 608 may beexecuted by the UE 400 to browse content and/or the Internet, forexample when the UE 400 is coupled to a network via a wireless link. Theweb browser application 608 may permit a user to enter information intoforms and select links to retrieve and view web pages. The media playerapplication 610 may be executed by the UE 400 to play audio oraudiovisual media. The JAVA applets 612 may be executed by the UE 400 toprovide a variety of functionality including games, utilities, and otherfunctionality.

FIG. 6B illustrates an alternative software environment 620 that may beimplemented by the DSP 502. The DSP 502 executes operating system kernel(OS kernel) 628 and an execution runtime 630. The DSP 502 executesapplications 622 that may execute in the execution runtime 630 and mayrely upon services provided by the application framework 624.Applications 622 and the application framework 624 may rely uponfunctionality provided via the libraries 626.

FIG. 7 illustrates a computer system 380 suitable for implementing oneor more embodiments disclosed herein. The computer system 380 includes aprocessor 382 (which may be referred to as a central processor unit orCPU) that is in communication with memory devices including secondarystorage 384, read only memory (ROM) 386, random access memory (RAM) 388,input/output (I/O) devices 390, and network connectivity devices 392.The processor 382 may be implemented as one or more CPU chips.

It is understood that by programming and/or loading executableinstructions onto the computer system 380, at least one of the CPU 382,the RAM 388, and the ROM 386 are changed, transforming the computersystem 380 in part into a particular machine or apparatus having thenovel functionality taught by the present disclosure. It is fundamentalto the electrical engineering and software engineering arts thatfunctionality that can be implemented by loading executable softwareinto a computer can be converted to a hardware implementation bywell-known design rules. Decisions between implementing a concept insoftware versus hardware typically hinge on considerations of stabilityof the design and numbers of units to be produced rather than any issuesinvolved in translating from the software domain to the hardware domain.Generally, a design that is still subject to frequent change may bepreferred to be implemented in software, because re-spinning a hardwareimplementation is more expensive than re-spinning a software design.Generally, a design that is stable that will be produced in large volumemay be preferred to be implemented in hardware, for example in anapplication specific integrated circuit (ASIC), because for largeproduction runs the hardware implementation may be less expensive thanthe software implementation. Often a design may be developed and testedin a software form and later transformed, by well-known design rules, toan equivalent hardware implementation in an application specificintegrated circuit that hardwires the instructions of the software. Inthe same manner as a machine controlled by a new ASIC is a particularmachine or apparatus, likewise a computer that has been programmedand/or loaded with executable instructions may be viewed as a particularmachine or apparatus.

Additionally, after the system 380 is turned on or booted, the CPU 382may execute a computer program or application. For example, the CPU 382may execute software or firmware stored in the ROM 386 or stored in theRAM 388. In some cases, on boot and/or when the application isinitiated, the CPU 382 may copy the application or portions of theapplication from the secondary storage 384 to the RAM 388 or to memoryspace within the CPU 382 itself, and the CPU 382 may then executeinstructions that the application is comprised of. In some cases, theCPU 382 may copy the application or portions of the application frommemory accessed via the network connectivity devices 392 or via the I/Odevices 390 to the RAM 388 or to memory space within the CPU 382, andthe CPU 382 may then execute instructions that the application iscomprised of. During execution, an application may load instructionsinto the CPU 382, for example load some of the instructions of theapplication into a cache of the CPU 382. In some contexts, anapplication that is executed may be said to configure the CPU 382 to dosomething, e.g., to configure the CPU 382 to perform the function orfunctions promoted by the subject application. When the CPU 382 isconfigured in this way by the application, the CPU 382 becomes aspecific purpose computer or a specific purpose machine.

The secondary storage 384 is typically comprised of one or more diskdrives or tape drives and is used for non-volatile storage of data andas an over-flow data storage device if RAM 388 is not large enough tohold all working data. Secondary storage 384 may be used to storeprograms which are loaded into RAM 388 when such programs are selectedfor execution. The ROM 386 is used to store instructions and perhapsdata which are read during program execution. ROM 386 is a non-volatilememory device which typically has a small memory capacity relative tothe larger memory capacity of secondary storage 384. The RAM 388 is usedto store volatile data and perhaps to store instructions. Access to bothROM 386 and RAM 388 is typically faster than to secondary storage 384.The secondary storage 384, the RAM 388, and/or the ROM 386 may bereferred to in some contexts as computer readable storage media and/ornon-transitory computer readable media.

I/O devices 390 may include printers, video monitors, liquid crystaldisplays (LCDs), touch screen displays, keyboards, keypads, switches,dials, mice, track balls, voice recognizers, card readers, paper tapereaders, or other well-known input devices.

The network connectivity devices 392 may take the form of modems, modembanks, Ethernet cards, universal serial bus (USB) interface cards,serial interfaces, token ring cards, fiber distributed data interface(FDDI) cards, wireless local area network (WLAN) cards, radiotransceiver cards that promote radio communications using protocols suchas code division multiple access (CDMA), global system for mobilecommunications (GSM), long-term evolution (LTE), worldwideinteroperability for microwave access (WiMAX), near field communications(NFC), radio frequency identity (RFID), and/or other air interfaceprotocol radio transceiver cards, and other well-known network devices.These network connectivity devices 392 may enable the processor 382 tocommunicate with the Internet or one or more intranets. With such anetwork connection, it is contemplated that the processor 382 mightreceive information from the network, or might output information to thenetwork in the course of performing the above-described method steps.Such information, which is often represented as a sequence ofinstructions to be executed using processor 382, may be received fromand outputted to the network, for example, in the form of a computerdata signal embodied in a carrier wave.

Such information, which may include data or instructions to be executedusing processor 382 for example, may be received from and outputted tothe network, for example, in the form of a computer data baseband signalor signal embodied in a carrier wave. The baseband signal or signalembedded in the carrier wave, or other types of signals currently usedor hereafter developed, may be generated according to several methodswell-known to one skilled in the art. The baseband signal and/or signalembedded in the carrier wave may be referred to in some contexts as atransitory signal.

The processor 382 executes instructions, codes, computer programs,scripts which it accesses from hard disk, floppy disk, optical disk(these various disk based systems may all be considered secondarystorage 384), flash drive, ROM 386, RAM 388, or the network connectivitydevices 392. While only one processor 382 is shown, multiple processorsmay be present. Thus, while instructions may be discussed as executed bya processor, the instructions may be executed simultaneously, serially,or otherwise executed by one or multiple processors. Instructions,codes, computer programs, scripts, and/or data that may be accessed fromthe secondary storage 384, for example, hard drives, floppy disks,optical disks, and/or other device, the ROM 386, and/or the RAM 388 maybe referred to in some contexts as non-transitory instructions and/ornon-transitory information.

In an embodiment, the computer system 380 may comprise two or morecomputers in communication with each other that collaborate to perform atask. For example, but not by way of limitation, an application may bepartitioned in such a way as to permit concurrent and/or parallelprocessing of the instructions of the application. Alternatively, thedata processed by the application may be partitioned in such a way as topermit concurrent and/or parallel processing of different portions of adata set by the two or more computers. In an embodiment, virtualizationsoftware may be employed by the computer system 380 to provide thefunctionality of a number of servers that is not directly bound to thenumber of computers in the computer system 380. For example,virtualization software may provide twenty virtual servers on fourphysical computers. In an embodiment, the functionality disclosed abovemay be provided by executing the application and/or applications in acloud computing environment. Cloud computing may comprise providingcomputing services via a network connection using dynamically scalablecomputing resources. Cloud computing may be supported, at least in part,by virtualization software. A cloud computing environment may beestablished by an enterprise and/or may be hired on an as-needed basisfrom a third party provider. Some cloud computing environments maycomprise cloud computing resources owned and operated by the enterpriseas well as cloud computing resources hired and/or leased from a thirdparty provider.

In an embodiment, some or all of the functionality disclosed above maybe provided as a computer program product. The computer program productmay comprise one or more computer readable storage medium havingcomputer usable program code embodied therein to implement thefunctionality disclosed above. The computer program product may comprisedata structures, executable instructions, and other computer usableprogram code. The computer program product may be embodied in removablecomputer storage media and/or non-removable computer storage media. Theremovable computer readable storage medium may comprise, withoutlimitation, a paper tape, a magnetic tape, magnetic disk, an opticaldisk, a solid state memory chip, for example analog magnetic tape,compact disk read only memory (CD-ROM) disks, floppy disks, jump drives,digital cards, multimedia cards, and others. The computer programproduct may be suitable for loading, by the computer system 380, atleast portions of the contents of the computer program product to thesecondary storage 384, to the ROM 386, to the RAM 388, and/or to othernon-volatile memory and volatile memory of the computer system 380. Theprocessor 382 may process the executable instructions and/or datastructures in part by directly accessing the computer program product,for example by reading from a CD-ROM disk inserted into a disk driveperipheral of the computer system 380. Alternatively, the processor 382may process the executable instructions and/or data structures byremotely accessing the computer program product, for example bydownloading the executable instructions and/or data structures from aremote server through the network connectivity devices 392. The computerprogram product may comprise instructions that promote the loadingand/or copying of data, data structures, files, and/or executableinstructions to the secondary storage 384, to the ROM 386, to the RAM388, and/or to other non-volatile memory and volatile memory of thecomputer system 380.

In some contexts, the secondary storage 384, the ROM 386, and the RAM388 may be referred to as a non-transitory computer readable medium or acomputer readable storage media. A dynamic RAM embodiment of the RAM388, likewise, may be referred to as a non-transitory computer readablemedium in that while the dynamic RAM receives electrical power and isoperated in accordance with its design, for example during a period oftime during which the computer system 380 is turned on and operational,the dynamic RAM stores information that is written to it. Similarly, theprocessor 382 may comprise an internal RAM, an internal ROM, a cachememory, and/or other internal non-transitory storage blocks, sections,or components that may be referred to in some contexts as non-transitorycomputer readable media or computer readable storage media.

While several embodiments have been provided in the present disclosure,it should be understood that the disclosed systems and methods may beembodied in many other specific forms without departing from the spiritor scope of the present disclosure. The present examples are to beconsidered as illustrative and not restrictive, and the intention is notto be limited to the details given herein. For example, the variouselements or components may be combined or integrated in another systemor certain features may be omitted or not implemented.

Also, techniques, systems, subsystems, and methods described andillustrated in the various embodiments as discrete or separate may becombined or integrated with other systems, modules, techniques, ormethods without departing from the scope of the present disclosure.Other items shown or discussed as directly coupled or communicating witheach other may be indirectly coupled or communicating through someinterface, device, or intermediate component, whether electrically,mechanically, or otherwise. Other examples of changes, substitutions,and alterations are ascertainable by one skilled in the art and could bemade without departing from the spirit and scope disclosed herein.

What is claimed is:
 1. A system comprising: a near field communication(NFC) tag coupled to a consumer product, the NFC tag being transformablefrom a first state to a second state based on a state of the consumerproduct being transitioned from a first state to a second state; and aserver program stored on a non-transitory storage medium that, whenexecuted by a server apparatus, receives a first tag report from a userdevice in response to the NFC tag being tapped while being in the firststate, sends a first response from the server apparatus to the userdevice or another user device, or prompts another server apparatus tosend the first response to the user device or another user device, inresponse to the first tag report being received, receives a second tagreport from the user device or another user device in response to theNFC tag being tapped while being in the second state, the first tagreport differing from the second tag report, and sends a second responsefrom the server apparatus to the user device or another user device, orprompts another server apparatus to send the second response to the userdevice or another user device, in response to the second tag reportbeing received, the second response differing from the first response.2. The system of claim 1, further comprising the user device, whereinthe user device taps the NFC tag, and wherein the tapping involvessending an initiation message from the user device to the NFC tag andsending a reaction message from the NFC tag to the user device.
 3. Thesystem of claim 2, wherein the NFC tag comprises at least one loop andthe NFC tag is configured to send a first reaction message to the userdevice when the at least one loop is intact, wherein the loop isbreakable by a consumer manipulating the consumer product, and whereinthe NFC tag is configured to send a second reaction message to the userdevice when the loop is broken.
 4. The system of claim 2, wherein thenear field communication tag comprises at least one loop, and the userdevice is configured to send the first tag report to the serverapparatus when the at least one loop is intact, wherein the loop isbreakable by a consumer manipulating the consumer product, and whereinthe user device is configured to send the second tag report to theserver apparatus when the loop is broken.
 5. The system of claim 3,wherein the consumer product is a container closure for closing acontainer, and the NFC tag is configured such that the loop is brokenwhen a consumer removes the closure from the container.
 6. The system ofclaim 5, wherein the NFC tag is provided on the inside of the containerclosure, and wherein the consumer product is a bottle lid.
 7. The systemof claim 1, wherein at least one of the first response or the secondresponse includes a uniform resource locator.
 8. The system of claim 1,wherein the consumer product is in the first state configured to be usedas a container closure for closing a container, and the consumer productis in the second state configured to be attached to a surface of anexternal object.
 9. The system of claim 1, wherein at least one of theuser device or the another user device is a smartphone or another typeof NFC reader.
 10. The system of claim 1, wherein the second tag reportincludes order information for ordering or re-ordering a product. 11.The system of claim 1, wherein the user device or the another userdevice displays a first website content upon receiving the firstresponse and the user device or the another user device displays asecond website content, differing from the first website content, uponreceiving the second response.
 12. A method comprising: tapping a nearfield communication (NFC) tag coupled to a consumer product with a userdevice, the NFC tag transformable from a first state to a second statewithout updating or writing to the NFC tag; receiving, by a serverprogram stored on a non-transitory storage medium and executed by aserver apparatus, a tag report comprising registration information fromthe user device in response to the NFC tag being tapped by the userdevice while in the first state; sending, by the server program, a firstresponse from the server apparatus to the user device or another userdevice, or prompting another server apparatus to send the first responseto the user device or another user device, in response to the tag reportcomprising the registration information being received; receiving, bythe server program, an indication from the user device or another userdevice that the NFC tag is to be transformed to a dash cap in responseto sending the first response, wherein the NFC tag is transformed fromthe first state to the second state based on receipt of the indication;and sending, by the server program, a second response from the serverapparatus to the user device or another user device, or promptinganother server to send the second response to the user device or anotheruser device in response to receiving the indication, the second responsediffering from the first response.
 13. The method of claim 12, whereinthe first response and the second response include different uniformresource locators.
 14. The method of claim 13, wherein the uniformresource locator included in the second response references a web pagethat enables ordering the consumer product.
 15. The method of claim 14,further comprising: tapping the NFC tag by the user device or anotheruser device after the NFC tag is transformed from the first state to thesecond state; receiving, by the server program, a second tag report fromthe user device or another user device in response to the NFC tag beingtapped while in the second state; and sending, by the server program, athird response from the server apparatus to the user device or anotheruser device, or prompting another server to send the third response inresponse to receiving the second tag report, wherein the third responsecomprises the uniform resource locator included in the second responsethat references the web page to enable ordering the consumer product.16. The method of claim 12, wherein the registration informationcomprises an identification number of the NFC tag.
 17. The method ofclaim 16, further comprising: confirming, by the server program, that auniform resource locator specified by the NFC tag is correct and theidentification number of the NFC tag corresponds to one of a pluralityof identification numbers stored in a database, wherein the firstresponse is sent in response to the confirmation.
 18. A systemcomprising: a near field communication (NFC) tag coupled to a consumerproduct, the NFC tag being transformable from a first state to a secondstate without updating or writing to the NFC tag; and a server programstored on a non-transitory storage medium that, when executed by aserver apparatus, receives a first tag report from a user device inresponse to the NFC tag being tapped, sends a first response from theserver apparatus to the user device or another user device, or promptsanother server apparatus to send the first response to the user deviceor another user device, in response to the first tag report beingreceived, receives a second tag report from the user device or anotheruser device in response to the NFC tag being tapped after the NFC tag istransformed from the first state to the second state, the first tagreport differing from the second tag report, and sends a second responsefrom the server apparatus to the user device or another user device, orprompts another server apparatus to send the second response to the userdevice or another user device, in response to the second tag reportbeing received, the second response differing from the first response.19. The system of claim 18, wherein the NFC tag comprises at least oneloop that is breakable and the NFC tag is transformable from the firststate to the second state based on a state of the consumer product beingtransitioned from a first state to a second state by a consumermanipulating the consumer product, wherein the NFC tag sends a firstreaction message to the user device when the at least one loop is intactand sends a second reaction message to the user device when the loop isbroken, and wherein the user device sends the first tag report to theserver apparatus when the at least one loop is intact and the userdevice sends the second tag report to the server apparatus when the loopis broken.
 20. The system of claim 18, wherein the first tag reportcomprises registration information, wherein the first response is sentfrom the server apparatus or another server is prompted to send thefirst response only after receiving the registration information, andwherein the server program is further configured to: receive anindication from the user device or another user device that the NFC tagis to be transformed to a dash cap in response to sending the firstresponse, wherein the NFC tag is transformed from the first state to thesecond state based on receipt of the indication.